Explain version choice on download page #1791
Conversation
_layouts/download.html
Outdated
| <h2>Which version of Scala should I choose?</h2> | ||
| <p>There are 2 distribution lines of Scala 3:</p> | ||
| <ul> | ||
| <li><strong>Scala Next</strong> - The <strong>default</strong> to be used by most users, containing the latest features, bug fixes and improvements.</li> |
There was a problem hiding this comment.
this perhaps can display the current LTS/Next version?
There was a problem hiding this comment.
That's a good idea, I'm not sure how to implement it with this templating engine though 😞
There was a problem hiding this comment.
its using jekyll for templating, (like ruby, variables magically exist when you define them)
maybe you can look at this snippet (how the frontpage renders the lts and next releases) which loops through all the "current releases" and then when it sees the right release assigns it to the appropriate variable, then you can splice later with {{scala_lts_version}}
scala-lang/_layouts/frontpage.html
Lines 48 to 62 in 37767b2
There was a problem hiding this comment.
Thank you Jamie, that helped! the updated layout renders version numbers as on this screenshot:
@lrytz it also removes the sethian parentheses 😉
_layouts/download.html
Outdated
| <p>There are 2 distribution lines of Scala 3:</p> | ||
| <ul> | ||
| <li><strong>Scala Next</strong> - The <strong>default</strong> to be used by most users, containing the latest features, bug fixes and improvements.</li> | ||
| <li><strong>Scala LTS</strong> - Advised to be used for publishing <strong>libraries</strong>. (Some especially conservative users might also choose it over Scala Next.)</li> |
There was a problem hiding this comment.
Mabye without the sethian parentheses?
There was a problem hiding this comment.
Sounds good to me
| <li><strong>Scala LTS</strong> - Advised to be used for publishing <strong>libraries</strong>. (Some especially conservative users might also choose it over Scala Next.)</li> | |
| <li><strong>Scala LTS</strong> - Advised to be used for publishing <strong>libraries</strong>.</li> |
This is a follow up to #1790
Last year the advisory board has accepted https://github.com/scalacenter/advisoryboard/blob/main/proposals/032-scala-version-guidance.md that was later marked as completed in scalacenter/advisoryboard#164 by the introduction of https://scala-lang.org/development. While this page provides a clear guidance, it's very hard to find.
The proposal mentioned explaining version choice on the download page, this PR provides such guidance.